On-board vehicular communication system

ABSTRACT

A system and method of obtaining update information include receiving a request for an update from a mobile device, determining whether the request for update is for a scheduled update or an unscheduled update, in response to determining that the request for update is for an unscheduled update: requesting a first update information from a high-speed provider, receiving the first update information from the high-speed provider, and sending the first update information to the mobile device, and in response to determining the update is for a scheduled update: requesting a second update information from the telematics system, receiving the second update information from the telematics system, and sending the second update information to the mobile device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation application of U.S. patentapplication Ser. No. 15/684,664, entitled “ON-BOARD VEHICULARCOMMUNICATION SYSTEM,” filed on Aug. 23, 2017, the contents of which ishereby incorporated in their entirety by reference.

BACKGROUND

On-board vehicular communication systems allow drivers to communicatewith one or more call centers via wireless networks, such as CDMA, GSM,and LTE networks. Drivers may contact the call centers duringemergencies, summon road-side assistance, ask for navigation directions,and request vehicle diagnostics. Many on-board systems provide audiointerfaces to allow drivers to communicate with the call centers.Additionally, drivers may also rely on textual input/output or othermethods of communication.

To better assist drivers, the on-board systems may transmit globalpositioning system (GPS) data to the call centers to relay the vehicles'location. The GPS data may allow the call centers to provide fasterroad-side assistance and navigation directions, help locate lostvehicles, and offer recommendations for attractions and amenities in thevicinity of the vehicles.

Providers of the on-board communication systems may charge drivers feesfor using the systems. These fees may include one-time fees, per-usefees, and/or monthly/annual fees. The fees may cover subscriptions tothe wireless network, and call centers personnel and maintenance-relatedcharges, among other relevant expenses.

Some providers of the on-board vehicular communication systems providesoftware applications that allow drivers to remotely access the on-boardsystems via mobile devices. The drivers may install the softwareapplications on their personal mobile devices, and rely on theapplication interface to provide instructions and requests to theon-board vehicular communication systems. However, sending theseinstructions and requests over the communication networks may becomecostly, and improvements may be desirable.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DETAILEDDESCRIPTION. This summary is not intended to identify key features ofthe claimed subject matter, nor is it intended to be used as an aid indetermining the scope of the claimed subject matter.

Aspects of the present disclosure include receiving a request for anupdate from a mobile device, determining whether the update is ascheduled update or an unscheduled update, in response to determiningthat the update is an unscheduled update: requesting a first updateinformation from a high-speed provider, receiving the first updateinformation from the high-speed provider, and sending the first updateinformation to the mobile device, and in response to determining thatthe update is a scheduled update: requesting a second update informationfrom the telematics system, receiving the second update information fromthe telematics system, and sending the second update information to themobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed to be characteristic of aspects of thedisclosure are set forth in the appended claims. In the description thatfollows, like parts are marked throughout the specification and drawingswith the same numerals, respectively. The drawing figures are notnecessarily drawn to scale and certain figures may be shown inexaggerated or generalized form in the interest of clarity andconciseness. The disclosure itself, however, as well as a preferred modeof use, further objects and advantages thereof, will be best understoodby reference to the following detailed description of illustrativeaspects of the disclosure when read in conjunction with the accompanyingdrawings, wherein:

FIG. 1 illustrates a schematic view of an example operating environmentof a telematics system in accordance with aspects of the presentdisclosure;

FIG. 2 illustrates an example network for managing the telematicssystem;

FIG. 3 illustrates an example method of obtaining update information.

FIG. 4 illustrates another example method of obtaining updateinformation.

FIG. 5 illustrates yet another example method of obtaining updateinformation.

FIG. 6 illustrates an example method of determining when to reroutedata.

FIG. 7 illustrates an example method of sending up-to-date updateinformation.

FIG. 8 illustrates an example computer system in accordance with anaspect of the invention.

DETAILED DESCRIPTION

The following includes definitions of selected terms employed herein.The definitions include various examples and/or forms of components thatfall within the scope of a term and that may be used for implementation.The examples are not intended to be limiting.

A “processor,” as used herein, processes signals and performs generalcomputing and arithmetic functions. Signals processed by the processormay include digital signals, data signals, computer instructions,processor instructions, messages, a bit, a bit stream, or othercomputing that may be received, transmitted and/or detected.

A “bus,” as used herein, refers to an interconnected architecture thatis operably connected to transfer data between computer componentswithin a singular or multiple systems. The bus may be a memory bus, amemory controller, a peripheral bus, an external bus, a crossbar switch,and/or a local bus, among others. The bus may also be a vehicle bus thatinterconnects components inside a vehicle using protocols, such asController Area network (CAN), Local Interconnect Network (LIN), amongothers.

A “memory,” as used herein may include volatile memory and/ornon-volatile memory. Non-volatile memory may include, for example, ROM(read only memory), PROM (programmable read only memory), EPROM(erasable PROM) and EEPROM (electrically erasable PROM). Volatile memorymay include, for example, RAM (random access memory), synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), and/or direct RAM bus RAM (DRRAM).

An “operable connection,” as used herein may include a connection bywhich entities are “operably connected”, is one in which signals,physical communications, and/or logical communications may be sentand/or received. An operable connection may include a physicalinterface, a data interface and/or an electrical interface.

A “vehicle,” as used herein, refers to any moving vehicle that ispowered by any form of energy. A vehicle may carry human occupants orcargo. The term “vehicle” includes, but is not limited to: cars, trucks,vans, minivans, SUVs, motorcycles, scooters, ATVs, boats, personalwatercraft, and aircraft. In some cases, a motor vehicle includes one ormore engines.

An on-board telematics system may enable a driver to remotely obtainvehicle information and control his vehicle via a wireless network.Repeated access to the telematics systems may become costly, however, assome wireless carriers may charge the driver on a per-use or per-minutebasis. When using a telematics system with access to wireless networksvia multiple carriers, a driver may communicate routine information overa network by a carrier with a slower connection and time-sensitiveinformation over another network by carrier with a faster connection.

Turning to FIG. 1, a schematic view of an example operating environment100 of a vehicle telematics system 110 according to an aspect of thedisclosure is provided. The vehicle telematics system 110 may residewithin a vehicle 102. The components of the vehicle telematics system110, as well as the components of other systems, hardware architectures,and software architectures discussed herein, may be combined, omitted ororganized into various implementations.

The vehicle 102 may generally include an electronic control unit (ECU)122 that operably controls a plurality of vehicle systems. The vehiclesystems may include, but are not limited to, the vehicle telematicssystem 110, among others, including vehicle HVAC systems, vehicle audiosystems, vehicle video systems, vehicle infotainment systems, vehicletelephone systems, vehicle control systems, and the like.

The vehicle 102 may further include a communications device 124 (e.g.,wireless modem) for providing wired or wireless computer communicationsutilizing various protocols to send/receive electronic signalsinternally with respect to features and systems within the vehicle 102and with respect to external devices. These protocols may include awireless system utilizing radio-frequency (RF) communications (e.g.,IEEE 802.11 (Wi-Fi), IEEE 802.15.1 (Bluetooth®)), a near fieldcommunication system (NFC) (e.g., ISO 13157), a local area network(LAN), a wireless wide area network (WWAN) (e.g., cellular) and/or apoint-to-point system. Additionally, the communications device 124 ofthe vehicle 102 may be operably connected for internal computercommunication via a bus (e.g., a CAN or a LIN protocol bus) tofacilitate data input and output between the electronic control unit 122and vehicle features and systems. In an aspect, the communicationsdevice 124 may be configured for vehicle-to-vehicle (V2V)communications. For example, V2V communications may include wirelesscommunications over a reserved frequency spectrum. As another example,V2V communications may include an ad hoc network between vehicles set upusing Wi-Fi or Bluetooth®.

In some implementations, the vehicle telematics system 110 may include adiagnostic device 118 and one or more sensors 120. The diagnostic device118 may obtain information from the sensors 120. The sensors 120 may bedisposed throughout the vehicle 102, and collect information such asfuel quantity, fuel range, speedometer reading, odometer reading, doorlocks status, global positioning system (GPS) data, entertainment systemdata, tire pressure reading, battery reading, fluid level, and otherinformation relevant to the operation of the vehicle 102.

FIG. 2 illustrates an example network 200 for managing the telematicssystem 110. The network 200 may be a communications network thatfacilitates communications among multiple systems. For example, thenetwork 200 may include the Internet or another Internet Protocol (IP)based network. The network 200 may enable the telematics system 110 tocommunicate with a mobile device 210, a low-speed provider 220, or ahigh-speed provider 230. The telematics system 110 within the vehicle102 may communicate with the network 200 via the communications device124. The low-speed provider and the high-speed provider 220, 230 mayeach include a computer system, as shown with respect to FIG. 8described below, associated with one or more vehicle manufacturers, oneor more telematics system manufacturers, dealers, streaming serviceproviders, and/or internet service providers. In certain aspects, thehigh-speed provider 230 may exchange information with the telematicssystem 110 faster than the low-speed provider 220. In some examples, thelow-speed provider 220 may belong to the one or more vehiclemanufacturers. The high-speed provider 230 may belong to a third-partyentity.

Turning now to FIG. 3, in some implementations, the mobile device 210may optionally request (304) a scheduled update from the telematicssystem 110. The mobile device 210 may be associated with the driver ofthe vehicle 102. The scheduled update may occur when the driveractivates the mobile device 210 and/or loads software that connects tothe telematics system 110. In certain aspects, the mobile device 210 mayroutinely request scheduled updates from the telematics system 110. Forexample, the mobile device 210 may request scheduled updates every 1, 2,3, 5, 10, 20, 30, 50, or 60 minutes, among other intervals. The requestfor scheduled updates may require information such as amount of fuel,fuel range, speedometer reading, odometer reading, door locks status,global positioning system (GPS) data, entertainment system data, tirepressure reading, battery reading, and fluid levels, among otherinformation relevant to the operation of the vehicle 102.

Next, the low-speed provider 230 may optionally request (306) updateinformation from the telematics system 100. The request for updateinformation may be transmitted in response to the request for thescheduled update by the mobile device 210.

In certain aspects, the telematics system 110 may optionally receive(308) the request for update information. Upon receiving (308) therequest, the telematics system 110 may collect the information from thediagnostic device 118 and the sensors 120, and/or the memory 116.

Once the update information has been collected, in some aspects, thetelematics system 110 may send (310) the update information to thelow-speed provider 230. The update information may include some or allof the information in the request for scheduled update. In certainaspects, the telematics system 110 may send (310) additional informationto the low-speed provider 230, such as information not relevant to therequest for scheduled update. The telematics system 110 may determine,based on computer programs stored in the memory 116 and executed by theprocessor 114, that the additional information is relevant to thelow-speed provider 230 and/or the driver using the mobile device (210).The computer programs may be pre-programmed by the manufacturer of thevehicle 102, or programmed by the dealer or the driver of the vehicle102. Examples of the additional information include maintenancereminders, mechanical warnings, and service requests.

In some aspects, the telematics system 110 may send (310) updateinformation to the low-speed provider 230 without receiving (308) arequest. For example, the telematics system 110 may send (310) updateinformation after the vehicle 102 drives for a certain distance, such as1, 2, 5, 10, 20, or 50 miles, among other distances. Alternatively, thetelematics system 110 may send (310) update information every 1, 2, 3,5, 10, 20, 30, 50, or 60 minutes, among other intervals, during theoperation of the vehicle 102. In yet another example, the telematicssystem 110 may send (310) update information every time an event occurs,such as vehicle start, vehicle shut-off, warning light activation,mechanical maintenance/service, airbag deployment, or other events.

In some implementations, the low-speed provider 230 receives (312) theupdate information from the telematics server 110.

After receiving the information, the low-speed provider 230 may send(314) the scheduled update to the mobile device 210.

Next, the mobile device 210 may receive (316) the scheduled update. Thescheduled update may be stored in a log in the mobile device 210.

In some implementations, the driver may initiate an unscheduled update.For example, the driver may want to know the mileage of the vehicle 102by accessing the odometer reading. In another example, the driver maywant to know the fluid level and battery reading to determine whetherthe vehicle 102 requires maintenance. In yet another example, the drivermay initiate an unscheduled update to obtain GPS data to locate thevehicle 102. In an aspect, the mobile device 210 may request (318) anunscheduled update from the telematics system 110.

In response to the request for the unscheduled update, in someimplementations, the low-speed provider 230 may request (320) the updateinformation from the high-speed provider 220 to fulfill the driver'srequest faster.

Next, the telematics system 110 may receive (324) the request for theupdate information, and the telematics system 110 may collect theinformation from the diagnostic device 118, the sensors 120, and/or thememory 116. For example, the telematics system 110 may obtain theodometer reading via the CAN. In another example, the telematics system110 may instantiate the diagnostic device 118 to obtain fluid levels andbattery reading from the sensors 120. In yet another example, thetelematics system 110 may access the memory 116 to obtain the GPS dataof the last known location of the vehicle 102.

After obtaining the requested update information, the telematics system110 may send (326) the update information to the high-speed provider220.

Next, the high-speed provider 220 may receive (328) the updateinformation from the telematics system 110.

In the next block, the high-speed provider 220 may send (330) the updateinformation to the low-speed provider 230 via wired or wirelessnetworks.

The low-speed provider 230, in certain implementations, may receive(332) the update information from the high-speed provider 220.

Upon receiving the update information, in some aspects, the low-speedprovider 230 may send (334) the unscheduled update to the mobile device210 based on the update information.

In an aspect, the mobile device 210 of the driver may receive (336) theunscheduled update from the low-speed provider 230. The scheduled updatemay be stored in a log in the mobile device 210.

Turning now to FIG. 4, in some implementations, the mobile device 210may optionally request (404) a scheduled update from the telematicssystem 110.

The low-speed provider 230 may optionally request (406) updateinformation from the telematics system 100. The request for updateinformation may be transmitted in response to the request for thescheduled update by the mobile device 210.

In certain aspects, the telematics system 110 may optionally receive(408) the request for update information. Upon receiving (408) therequest, the telematics system 110 may collect the information from thediagnostic device 118, the sensors 120, and/or the memory 116.

Once the update information has been collected, in some aspects, thetelematics system 110 sends (410) the update information to thelow-speed provider 230. The update information may include some or allof the information in the request for scheduled update.

In some aspects, the telematics system 110 may send (410) updateinformation to the low-speed provider 230 without receiving (408) arequest. For example, the telematics system 110 may routinely send (410)update information to the low-speed provider 230 as described above.

In some implementations, the low-speed provider 230 receives (412) theupdate information from the telematics server 110.

After receiving the information, the low-speed provider 230 may send(414) the scheduled update to the mobile device 210.

Next, the mobile device 210 may receive (416) the scheduled update. Thescheduled update may be stored in a log in the mobile device 210.

In some implementations, the driver may initiate an unscheduled update.In an aspect, the mobile device 210 may request (418) an unscheduledupdate from the telematics system 110 via the high-speed provider 220.

In response to the request for an unscheduled update, in someimplementations, the high-speed provider 220 may request (420) theupdate information.

Next, the telematics system 110 may receive (422) the request for theupdate information and the telematics system 110 may collect theinformation from the diagnostic device 118 and the sensors 120, and/orthe memory 116.

After obtaining the requested update information, the telematics system110 may send (424) the update information to the high-speed provider220.

Next, the high-speed provider 220 may receive (426) the updateinformation from the telematics system 110.

In some aspects, the high-speed provider 220 may send (428) theunscheduled update to the mobile device 210 based on the updateinformation.

The mobile device 210 of the driver may receive (430) the unscheduledupdate from the low-speed provider 230.

Turning now to FIG. 5, in some aspects, the low-speed provider 230 mayreceive (502) a request for update from the mobile device 210. Therequest for update may be for a scheduled update and/or an unscheduledupdate.

The low-speed provider 230 determines (504) if the request for update isfor a scheduled or unscheduled update. The scheduled update may includeperiodic updates, routine updates, and/or event-triggered updates asdescribed above. The unscheduled update may be initiated by the driverof the vehicle 102. The low-speed provider 230 may determine based onalgorithms stored in the memory 116 and executed by the processor 114.

In some implementations, for the unscheduled update, the low-speedprovider 230 may request (506) update information from the high-speedprovider 220.

Next, the low-speed provider 230 may receive (508) the updateinformation from the high-speed provider 220.

Upon receiving the update information, in some aspects, the low-speedprovider 230 may send (510) the unscheduled update to the mobile device210 based on the update information.

Alternatively, the if low-speed provider 230 determines (504) that therequest for update is for a scheduled update, the low-speed provider 230may bypass the high-speed provider 220 and communicate with thetelematics system 110 directly.

In some implementations, for the unscheduled update, the low-speedprovider 230 may request (512) update information from the telematicssystem 110.

Next, the low-speed provider 230 may receive (514) the updateinformation from the high-speed provider 220.

Upon receiving the update information, in some aspects, the low-speedprovider 230 may send (516) the scheduled update to the mobile device210 based on the update information.

In other aspects, as shown in FIG. 6, the low-speed provider 230 mayutilize the high-speed provider 220 for unscheduled and scheduledupdates, and selectively utilize the bypass methods shown in FIGS. 3-5.The low-speed provider 230 may determine if the driver's subscriptionplan meets or fails to meet certain criteria before performing themethods shown in FIGS. 3-5. For example, if low-speed provider 230determines (602) that the amount of data in the driver's subscriptionplan with the high-speed provider 220 decreases below a predeterminedthreshold, the low-speed provider 230 may reroute (608) the unscheduledupdates through the high-speed provider 220 and the scheduled updatesthrough the low-speed provider 230 to conserve data. In other aspects,if low-speed provider 230 determines (604) that any communication withthe high-speed provider 220 may incur roaming charges, the low-speedprovider 230 may reroute (608) the unscheduled updates through thehigh-speed provider 220 and the scheduled updates through the low-speedprovider 230 to reduce roaming charges associated with the high-speedprovider 220. In yet another example, if the low-speed provider 230determines (606) that any communication with the high-speed provider 220during a peak usage time may incur additional charges, the low-speedprovider 230 may reroute (608) the unscheduled updates through thehigh-speed provider 220 and the scheduled updates through the low-speedprovider 230 to reduce the additional charges associated with the peakusage time.

Referring now to FIG. 7, the low-speed provider 230 may receive (702) afirst update information from the high-speed provider 220, and receive(704) a second update information from the telematics system 110. Thefirst update information and the second update information mayoptionally include one or more of the following: a timestamp, anodometer reading, and a fuel reading. Next, the low-speed provider 230may optionally determine (706) up-to-date update information between thefirst update information and the second update information using thetimestamps. For example, up-to-date update information may include amore recent timestamp. Alternatively, or additionally, the low-speedprovider 230 may optionally determine (708) up-to-date updateinformation between the first update information and the second updateinformation using the odometer readings. For example, up-to-date updateinformation may include a higher odometer reading. Alternatively, oradditionally, the low-speed provider 230 may optionally determine (710)the up-to-date update information between the first update informationand the second update information using the fuel readings. For example,the up-to-date update information may include a lower fuel reading.After determining the up-to-date update information, between the firstand the second update information, the low-speed provider 230 may send(712) the up-to-date update information to the mobile device 210.

Aspects of the present invention may be implemented using hardware,software, or a combination thereof and may be implemented in one or morecomputer systems or other processing systems. In an aspect of thepresent invention, features are directed toward one or more computersystems capable of carrying out the functionality described herein. Anexample of such a computer system 900 is shown in FIG. 8.

Computer system 900 includes one or more processors, such as processor904. The processor 904 is connected to a communication infrastructure906 (e.g., a communications bus, cross-over bar, or network). Varioussoftware aspects are described in terms of this example computer system.After reading this description, it will become apparent to a personskilled in the relevant art(s) how to implement aspects of the inventionusing other computer systems and/or architectures.

Computer system 900 may include a display interface 902 that forwardsgraphics, text, and other data from the communication infrastructure 906(or from a frame buffer not shown) for display on a display unit 930.Computer system 900 also includes a main memory 908, preferably randomaccess memory (RAM), and may also include a secondary memory 910. Thesecondary memory 910 may include, for example, a hard disk drive 912,and/or a removable storage drive 914, representing a floppy disk drive,a magnetic tape drive, an optical disk drive, a universal serial bus(USB) flash drive, etc. The removable storage drive 914 reads fromand/or writes to a removable storage unit 918 in a well-known manner.Removable storage unit 918 represents a floppy disk, magnetic tape,optical disk, USB flash drive etc., which is read by and written toremovable storage drive 914. As will be appreciated, the removablestorage unit 918 includes a computer usable storage medium having storedtherein computer software and/or data.

Alternative aspects of the present invention may include secondarymemory 910 and may include other similar devices for allowing computerprograms or other instructions to be loaded into computer system 900.Such devices may include, for example, a removable storage unit 922 andan interface 920. Examples of such may include a program cartridge andcartridge interface (such as that found in video game devices), aremovable memory chip (such as an erasable programmable read only memory(EPROM), or programmable read only memory (PROM)) and associated socket,and other removable storage units 922 and interfaces 920, which allowsoftware and data to be transferred from the removable storage unit 922to computer system 900.

Computer system 900 may also include a communications interface 924.Communications interface 924 allows software and data to be transferredbetween computer system 900 and external devices. Examples ofcommunications interface 924 may include a modem, a network interface(such as an Ethernet card), a communications port, a Personal ComputerMemory Card International Association (PCMCIA) slot and card, etc.Software and data transferred via communications interface 924 are inthe form of signals 928, which may be electronic, electromagnetic,optical or other signals capable of being received by communicationsinterface 924. These signals 928 are provided to communicationsinterface 924 via a communications path (e.g., channel) 926. This path926 carries signals 928 and may be implemented using wire or cable,fiber optics, a telephone line, a cellular link, a radio frequency (RF)link and/or other communications channels. In this document, the terms“computer program medium” and “computer usable medium” are used to refergenerally to media such as a removable storage drive 918, a hard diskinstalled in hard disk drive 912, and signals 928. These computerprogram products provide software to the computer system 900. Aspects ofthe present invention are directed to such computer program products.

Computer programs (also referred to as computer control logic) arestored in main memory 908 and/or secondary memory 910. Computer programsmay also be received via communications interface 924. Such computerprograms, when executed, enable the computer system 900 to perform thefeatures in accordance with aspects of the present invention, asdiscussed herein. In particular, the computer programs, when executed,enable the processor 904 to perform the features in accordance withaspects of the present invention. Accordingly, such computer programsrepresent controllers of the computer system 900.

In an aspect of the present invention where the invention is implementedusing software, the software may be stored in a computer program productand loaded into computer system 900 using removable storage drive 914,hard drive 912, or communications interface 920. The control logic(software), when executed by the processor 904, causes the processor 904to perform the functions described herein. In another aspect of thepresent invention, the system is implemented primarily in hardwareusing, for example, hardware components, such as application specificintegrated circuits (ASICs). Implementation of the hardware statemachine so as to perform the functions described herein will be apparentto persons skilled in the relevant art(s).

It will be appreciated that various implementations of theabove-disclosed and other features and functions, or alternatives orvarieties thereof, may be desirably combined into many other differentsystems or applications. Also that various presently unforeseen orunanticipated alternatives, modifications, variations, or improvementstherein may be subsequently made by those skilled in the art which arealso intended to be encompassed by the following claims.

What is claimed is:
 1. A method of sending up-to-date update informationto a mobile device, comprising: receiving a first update informationfrom a high-speed provider; receiving a second update information from atelematics system; determining a more recent one of the first updateinformation and the second update information; and providing the morerecent one of the first update information and the second updateinformation as the up-to-date update information to the mobile device.2. The method of claim 1, wherein: the first update information includesa first odometer reading; the second update information includes asecond odometer reading; and determining the up-to-date updateinformation includes determining an update information with a higherodometer reading based on the first odometer reading and the secondodometer reading.
 3. The method of claim 1, wherein: the first updateinformation includes a first timestamp; the second update informationincludes a second timestamp; and determining the up-to-date updateinformation includes determining an update information with a morerecent timestamp based on the first timestamp and the second timestamp.4. The method of claim 1, wherein: the first update information includesa first fuel reading; the second update information includes a secondfuel reading; and determining the up-to-date update information includesdetermining an update information with a lower fuel reading based on thefirst fuel reading and the second fuel reading.
 5. The method of claim1, wherein the high-speed provider is associated with a streamingcompany.
 6. The method of claim 1, further comprising receiving aplurality of scheduled updates during an operation of the vehicle. 7.The method of claim 6, wherein the plurality of scheduled updates occursduring a vehicle start, a vehicle shut-off, a warning light activation,a mechanical service, or an airbag deployment.
 8. A computer system forobtaining up-to-date update information from a telematics system in avehicle, comprising: a memory comprising instructions; and one or moreprocessors configured to execute the instructions to perform thefunctions of: receiving a first update information from a high-speedprovider; receiving a second update information from a telematicssystem; determining a more recent one of the first update informationand the second update information; and providing the more recent one ofthe first update information and the second update information as theup-to-date update information to the mobile device.
 9. The computersystem of claim 8, wherein: the first update information includes afirst odometer reading; the second update information includes a secondodometer reading; and determining the up-to-date update informationincludes determining an update information with a higher odometerreading based on the first odometer reading and the second odometerreading.
 10. The computer system of claim 8, wherein: the first updateinformation includes a first timestamp; the second update informationincludes a second timestamp; and determining the up-to-date updateinformation includes determining an update information with a morerecent timestamp based on the first timestamp and the second timestamp.11. The computer system of claim 8, wherein: the first updateinformation includes a first fuel reading; the second update informationincludes a second fuel reading; and determining the up-to-date updateinformation includes determining an update information with a lower fuelreading based on the first fuel reading and the second fuel reading. 12.The computer system of claim 8, wherein the high-speed provider isassociated with a streaming company.
 13. The computer system of claim 8,wherein the one or more processors are further configured to execute theinstructions to perform the function of receiving a plurality ofscheduled updates during an operation of the vehicle.
 14. The computersystem of claim 13, wherein the plurality of scheduled updates occursduring a vehicle start, a vehicle shut-off, a warning light activation,a mechanical service, or an airbag deployment.
 15. A non-transitorycomputer readable medium storing computer-executable instructions that,when executed by one or more processors of a computer, cause the one ormore processors to perform the method comprising: receiving a firstupdate information from a high-speed provider; receiving a second updateinformation from a telematics system; determining a more recent one ofthe first update information and the second update information; andproviding the more recent of the first update information and the secondupdate information as up-to-date update information to the mobiledevice.
 16. The computer readable medium of claim 15, wherein: the firstupdate information includes a first odometer reading; the second updateinformation includes a second odometer reading; and determining theup-to-date update information includes determining an update informationwith a higher odometer reading based on the first odometer reading andthe second odometer reading.
 17. The computer readable medium of claim15, wherein: the first update information includes a first timestamp;the second update information includes a second timestamp; anddetermining the up-to-date update information includes determining anupdate information with a more recent timestamp based on the firsttimestamp and the second timestamp.
 18. The computer readable medium ofclaim 15, wherein: the first update information includes a first fuelreading; the second update information includes a second fuel reading;and determining the up-to-date update information includes determiningan update information with a lower fuel reading based on the first fuelreading and the second fuel reading.
 19. The computer readable medium ofclaim 15, wherein the high-speed provider is associated with a streamingcompany.
 20. The computer readable medium of claim 15, furthercomprising instructions that, when executed by the one or moreprocessors of the computer, cause the one or more processors to performthe method of receiving a plurality of scheduled updates during anoperation of the vehicle.